|
Comment |
Description: Auditable execution of a trigger rule against an event. Usage: This transactional and auditable record is used in the 05 Collection and Evidence subject area as the authoritative representation of trigger execution data. It is referenced through Trigger Definition has Executions, Child Event has Trigger Executions. |
|
Name |
Comment |
|
Trigger Execution ID |
Description: Stable system identifier for a Trigger Execution record. Usage: Used as the conceptual primary identifier and as the stable reference from relationships to Trigger Execution. Required for every record. |
|
Evaluated At |
Description: Timestamp recording when the evaluated event occurred. Usage: Used for scheduling, recency rules, effective dating, audit history, and chronological reporting. Required for every record. |
|
Result |
Description: Business value storing result for the Trigger Execution record. Usage: Used by services, rules, search, reporting, or audit processing that operates on Trigger Execution records. Required for every record. |
|
Reason |
Description: Business value storing reason for the Trigger Execution record. Usage: Used by services, rules, search, reporting, or audit processing that operates on Trigger Execution records. Optional and recorded only when known or applicable. |
|
Generated Object Type |
Description: Controlled classification value for generated object type. Usage: Used to select business rules, validate compatible relationships, group records, filter queries, and drive user-interface behavior. Optional and recorded only when known or applicable. |
|
Generated Object Reference |
Description: Traceable reference used to locate, correlate, or audit the generated object reference. Usage: Used for provenance, external integration, traceability, and reviewer verification. Optional and recorded only when known or applicable. |
|
Processing Status3 |
Description: Lifecycle or workflow status of the Trigger Execution record. Usage: Used to gate workflow transitions, exclude inactive or incomplete records, support operations dashboards, and preserve processing history. Required for every record. |
|
|
|